Skip to content

docs: add BBIS canonical definition artifact#827

Open
QueBallSharken wants to merge 5 commits into
OWASP:mainfrom
QueBallSharken:bbis-definition-doc
Open

docs: add BBIS canonical definition artifact#827
QueBallSharken wants to merge 5 commits into
OWASP:mainfrom
QueBallSharken:bbis-definition-doc

Conversation

@QueBallSharken
Copy link
Copy Markdown

This PR adds a bounded canonical definition artifact for Boundary-to-Boundary Invariant Survival (BBIS).

Purpose:

  • preserve the BBIS formulation precisely
  • distinguish BBIS from adjacent concepts
  • keep the term reviewable as a bounded continuity requirement and evaluation criterion
  • avoid overclaiming BBIS as a full concrete architecture

This artifact is intentionally scoped to:

  • the core BBIS definition
  • canonical terms
  • minimum serious conditions
  • failure classes
  • conformance levels
  • public claim discipline

It is intentionally not framed as:

  • a generic synonym for authorization correctness
  • a generic synonym for attestation validity
  • a generic synonym for receipt correctness
  • a full implementation architecture

Document the Authority Collapse Mode specification outlining its principles, core axioms, and deployment criteria.

Introduces the Authority Collapse Mode (ACM) specification.

Defines override scope as a separately signed boundary input rather than contextual policy state.

Establishes boundary re-derivation semantics, canonical snapshot inputs, and open questions for future work.

Attribution: Steven Kyle Hensley.(Stevil)

Signed-off-by: Steven K. Hensley <twiztidsrh14@gmail.com>
Add Authority Collapse Mode specification document
Add canonical BBIS definition, classification, conformance levels, and claim discipline artifact.

Signed-off-by: Steven K. Hensley <twiztidsrh14@gmail.com>
Signed-off-by: Steven K. Hensley <twiztidsrh14@gmail.com>
docs: remove authority collapse mode spec from bbis artifact branch

Signed-off-by: Steven K. Hensley <twiztidsrh14@gmail.com>
@QueBallSharken
Copy link
Copy Markdown
Author

This PR is intentionally narrow.

It is meant to add a bounded canonical definition artifact for BBIS as:

  • primarily a continuity requirement
  • secondarily an evaluation criterion
  • not a concrete architecture by itself

I am intentionally keeping this PR scoped to the definition artifact rather than broadening it into adjacent formulations or implementation-specific mechanisms.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant